Support specifying a client certificate for mTLS auth #940
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using a reverse-proxy with mTLS (client authentication) is a decent way to expose your self-hosted services on the internet.
This PR adds support for using a certificate that's installed in your Android device.
The changes are largely based on:
An optional client certificate can be selected when adding self-hosted accounts (FreshRSS, Google Reader and Fever APIs):
It can later be changed/removed when viewing the account details:
I'm comfortable with the logic changes, but I have not much experience with Compose, so my code there can be sub-optimal.